tut2.exe -port 8888This will start the
tut2.CGI
application server and it will listen to port 8888 for processing requests. Once the application server is running you should be able to test your application just like a CGI application (Pressing the Test button). Note that you may have to clear your browser's cache to be sure your are running against an Application server and not a CGI.
If you need to rebuild your project after making changes you must kill the application server before re-linking and start it again after linking. You do not have to stop and start your Netscape server. You can use the Sapphire Application Manager Console (see below) to shutdown an application server gracefully.
$SAPPHIRE/config/apserver.txt
obj.conf
is correct. You will need to restart your web server if you change obj.conf
. The line where you specify the configuration file name in obj.conf
should look something like this:
Init fn="sapphire-init" file="/usr/sapphire/config/apserver.txt"
saappman
) is running on the host where the application server is supposed to run. If you are using windows verify that the Sapphire Application Server Manager Service has been installed on the host with the Sapphire Gateway Manager.
-port [port number]
command line parameter. You should try every port specified in the configuration file. The program will complain if the port is already in use. Try using different port numbers until your application server does not print an error message. When an application server successfully starts it will not print any output, it will just wait to process a request. Once you find ports that will work be sure to put the proper ports back into your configuration file.